Package | ehealthplatform.be.r4.federalprofiles |
Type | StructureDefinition |
Id | Id |
FHIR Version | R4 |
Source | https://www.ehealth.fgov.be/standards/fhir/https://simplifier.net/resolve?scope=ehealthplatform.be.r4.federalprofiles@1.3.3-beta&canonical=https://www.ehealth.fgov.be/standards/fhir/StructureDefinition/be-observation |
Url | https://www.ehealth.fgov.be/standards/fhir/StructureDefinition/be-observation |
Version | 1.0.0 |
Status | active |
Name | BeObservation |
Experimental | False |
Authority | hl7 |
Description | Belgian federal profile for an observation. Initially based on the functional description of the NIHDI. As Observation is used in many instances in FHIR, please refer to the HL7 specs of the base resource for guidance around expression of actual values using UCUM, methods, location on body etc. Special remarks for KMEHR users: The FHIR Observation resource captures many things that are in a KMEHR message structured as an 'item'. This includes things like 'vital signs such as body weight, blood pressure, and temperature […], personal characteristics such as eye-color […] social history like tobacco use, family support, or cognitive status […]' ( https://www.hl7.org/fhir/R4/observation.html ) For some of these things, HL7 already has worked out profiles and they SHALL be used when such a use case is needed. Specifically, projects SHALL take note of the existing profiles described on https://www.hl7.org/fhir/R4/observation-vitalsigns.html |
Type | Observation |
Kind | resource |
No resources found
StructureDefinition | |
be-observationcodeableconcept | BeObservationCodeableConcept |
be-organization | BeOrganization |
be-patient | BePatient |
be-practitioner | BePractitioner |
be-practitionerrole | BePractitionerRole |
{
"resourceType" : "StructureDefinition",
"id" : "be-observation",
"url" : "https://www.ehealth.fgov.be/standards/fhir/StructureDefinition/be-observation",
"version" : "1.0.0",
"name" : "BeObservation",
"status" : "active",
"description" : "Belgian federal profile for an observation. Initially based on the functional description of the NIHDI.\r\nAs Observation is used in many instances in FHIR, please refer to the HL7 specs of the base resource for guidance around expression of actual values using UCUM, methods, location on body etc.\r\n\r\nSpecial remarks for KMEHR users:\r\nThe FHIR Observation resource captures many things that are in a KMEHR message structured as an 'item'. This includes things like 'vital signs such as body weight, blood pressure, and temperature [â¦], personal characteristics such as eye-color [â¦] social history like tobacco use, family support, or cognitive status [â¦]' ( https://www.hl7.org/fhir/R4/observation.html )\r\nFor some of these things, HL7 already has worked out profiles and they SHALL be used when such a use case is needed. Specifically, projects SHALL take note of the existing profiles described on https://www.hl7.org/fhir/R4/observation-vitalsigns.html",
"fhirVersion" : "4.0.0",
"kind" : "resource",
"abstract" : false,
"type" : "Observation",
"baseDefinition" : "http://hl7.org/fhir/StructureDefinition/Observation",
"derivation" : "constraint",
"differential" : {
"element" : [
{
"id" : "Observation.code",
"path" : "Observation.code",
"definition" : "Describes what was observed. Sometimes this is called the observation \"name\".\r\n\r\nFor providing systems, it is RECOMMENDED to express this using a code and consuming software SHALL record this.\r\nIn general, it shall be noted SNOMED-CT is the preferred national terminology. Other coding systems remain allowed or MAY be preferred in specific flows (e.g. the use of LOINC codes to express a laboratory test.)",
"type" : [
{
"code" : "CodeableConcept",
"profile" : [
"https://www.ehealth.fgov.be/standards/fhir/StructureDefinition/be-observationcodeableconcept"
]
}
],
"mustSupport" : true
},
{
"id" : "Observation.subject",
"path" : "Observation.subject",
"type" : [
{
"code" : "Reference",
"targetProfile" : [
"http://hl7.org/fhir/StructureDefinition/Patient",
"http://hl7.org/fhir/StructureDefinition/Group",
"http://hl7.org/fhir/StructureDefinition/Device",
"http://hl7.org/fhir/StructureDefinition/Location",
"https://www.ehealth.fgov.be/standards/fhir/StructureDefinition/be-patient"
]
}
]
},
{
"id" : "Observation.performer",
"path" : "Observation.performer",
"comment" : "References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.\r\n\r\nSpecial remarks for KMEHR users:\r\nIn a KMEHR context, this would be 'author'.",
"min" : 1,
"type" : [
{
"code" : "Reference",
"targetProfile" : [
"http://hl7.org/fhir/StructureDefinition/Practitioner",
"http://hl7.org/fhir/StructureDefinition/PractitionerRole",
"http://hl7.org/fhir/StructureDefinition/Organization",
"http://hl7.org/fhir/StructureDefinition/CareTeam",
"http://hl7.org/fhir/StructureDefinition/Patient",
"http://hl7.org/fhir/StructureDefinition/RelatedPerson",
"https://www.ehealth.fgov.be/standards/fhir/StructureDefinition/be-patient",
"https://www.ehealth.fgov.be/standards/fhir/StructureDefinition/be-organization",
"https://www.ehealth.fgov.be/standards/fhir/StructureDefinition/be-practitionerrole",
"https://www.ehealth.fgov.be/standards/fhir/StructureDefinition/be-practitioner"
]
}
]
}
]
},
"text" : {
}
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.